Electronic subscriber identity module selection

ABSTRACT

Embodiments are described for identifying and accessing an electronic subscriber identity module (eSIM) and associated content of the eSIM in a multiple eSIM configuration. An embedded Universal Integrated Circuit Card (eUICC) can include multiple eSIMs, where each eSIM can include its own file structures and applications. Some embodiments include a processor of a mobile device transmitting a special command to the eUICC, including an identification that uniquely identifies an eSIM in the eUICC. After selecting the eSIM, the processor can access file structures and applications of the selected eSIM. The processor can then use existing commands to access content in the selected eSIM. The special command can direct the eUICC to activate or deactivate content associated with the selected eSIM. Other embodiments include an eUICC platform operating system interacting with eSIMs associated with logical channels to facilitate identification and access to file structures and applications of the eSIMs.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/005,870, filed May 30, 2014, and entitled “ELECTRONICSUBSCRIBER IDENTITY MODULE (eSIM) SELECTION,” which is incorporated byreference herein in its entirety for all purposes.

This application is related to U.S. patent application Ser. No.14/503,048, filed Sep. 30, 2014, entitled “Electronic SubscriberIdentity Module Application Identifier Handling” which is incorporatedby reference herein in its entirety for all purposes.

FIELD

The described embodiments generally relate to embedded UniversalIntegrated Circuit Cards (eUICCs) and electronic Subscriber IdentityModules (eSIMs). In particular, the described embodiments involveenabling a mobile device to access eSIM content in a multiple eSIMenvironment.

BACKGROUND

Most mobile devices are configured to receive and operate removableUniversal Integrated Circuit Cards (UICCs) that enable the mobiledevices to access services provided by mobile network operators (MNOs).In particular, each UICC includes at least a microprocessor and aread-only memory (ROM), where the ROM is configured to store differentapplets and authentication data that the mobile device can utilize toregister and interact with the MNOs. Typically, a UICC takes the form ofa small removable card (e.g., a SIM card) that is configured to store asingle MNO profile and be inserted into a UICC-receiving bay included ina mobile device. In more recent implementations, however, UICCs arebeing embedded directly into system boards of mobile devices and areconfigured to store multiple MNO profiles, referred to herein aselectronic SIMs (eSIMs). For example, an embedded UICC (eUICC) can storeone eSIM for a local MNO and another eSIM for an international MNO.Notably, these eUICCs provide several advantages over traditional,removable UICCs. For example, some eUICCs include a rewritable memorythat can facilitate eSIM updates for accessing extended featuresprovided by MNOs. The eUICCs also eliminate the necessity of includingUICC-receiving bays within mobile devices. The implementation of eUICCstherefore not only increases the flexibility of mobile devices, but alsosimplifies their design and frees up space for other components.

Although eUICCs provide many benefits over traditional, removable UICCs,implementing eUICCs present new challenges with respect to how eSIMcontent is accessed by mobile devices. For example, MNOs share many ofthe same properties as one another, and, as a result, eSIMs can ofteninclude applications that share the same application identifier (AID).Consequently, a mobile device whose eUICC includes two or more eSIMsthat share similarities may not be able to successfully select andaccess an application of a particular one of the two or more eSIMs. Morespecifically, existing protocols for accessing applications involvereferencing only the AID, which is not sufficient for the mobile deviceto access an application of a particular eSIM because the AID alone doesnot uniquely identify the application of the particular eSIM thatincludes the application. Therefore, there exists a need for enabling amobile device—specifically, a processor included in the mobile device—toaccess specific eSIM content, such as an application of a particulareSIM, in a multiple eSIM environment.

SUMMARY

An eUICC can store multiple eSIMs, and each eSIM can store its owncontent (e.g., applications and file structures). With thisconfiguration of multiple eSIMs on the eUICC, however, a problem arises:how to identify and access the content of different eSIMs stored on thesame eUICC. For example, when the mobile device uses an existinginterface to send a read command for a file identified by a fileidentifier (FID), there can be a conflict because the same FID can existwithin multiple eSIMs. Consequently, the eUICC may not be capable ofaccessing the file for a specific eSIM using only the FID. Theembodiments set forth herein address this problem by introducing aspecial command that can be transmitted to the eUICC from the mobiledevice. Specifically, the special command includes an identifier thatuniquely identifies an eSIM to be selected, and can direct the eUICC toactivate or deactivate content included in the eSIM. After selecting aneSIM, the mobile device can view the content (e.g., applications andfile structures) of the eSIM. In this manner, the mobile device canaccess the content of a specific eSIM stored by an eUICC even whensimilarities exist across other eSIMs stored by the eUICC.

Additionally, conflicts can occur in the eUICC when attempting to accessan application based solely on an application identifier (AID)associated with the application. To cure this deficiency, logicalchannels can be used to separate the manner in which eSIMs are accessedby the eUICC. Logical channels are defined in existing standards suchthat the mobile device can open multiple logical channels to accessdifferent applications of an eSIM. More specifically, the existingstandards dictate that an application of an eSIM must first be selectedon a logical channel before the application can be accessed.Accordingly, an operating system (OS) executing on the eUICC has priorknowledge of the eSIM that is being selected on a logical channel. Theembodiments set forth herein expand this functionality to enable theselection of different eSIMs (as opposed to the applications themselves)on different logical channels. Subsequently, each application can beuniquely identified by the command SELECT (eSIM ID, AID). Terminals of amobile device (e.g., baseband processors) that interact with the eUICCcan be aware of the different eSIMs managed by the eUICC, e.g., bymanaging the various eSIM IDs. In this manner, the processor in themobile device can simultaneously access specific applications acrossmultiple eSIMs in the eUICC.

This Summary is provided merely for purposes of summarizing some exampleembodiments so as to provide a basic understanding of some aspects ofthe subject matter described herein. Accordingly, it will be appreciatedthat the above-described features are merely examples and should not beconstrued to narrow the scope or spirit of the subject matter describedherein in any way. Other features, aspects, and advantages of thesubject matter described herein will become apparent from the followingDetailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and arrangements for thedisclosed inventive apparatuses and methods for providing wirelesscomputing devices. These drawings in no way limit any changes in formand detail that may be made to the embodiments by one skilled in the artwithout departing from the spirit and scope of the embodiments. Theembodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings, wherein likereference numerals designate like structural elements.

FIG. 1 illustrates a block diagram of different components of a wirelesssystem including a MNO, base station and a mobile device configured toimplement the various techniques described herein, according to someembodiments.

FIG. 2 illustrates a block diagram of a more detailed view of particularcomponents of the system of FIG. 1, according to some embodiments.

FIG. 3A illustrates a block diagram of an eSIM, according to someembodiments.

FIG. 3B illustrates a block diagram of an eUICC that stores multipleeSIMs, according to some embodiments.

FIG. 3C illustrates a detailed view of a file structure of anapplication, according to some embodiments.

FIG. 4 illustrates a timing diagram for selecting an application of aspecific eSIM included in an eUICC, according to some embodiments.

FIG. 5A illustrates a timing diagram for selecting and accessing anapplication of an eSIM among multiple eSIMs that include theapplication, according to some embodiments.

FIG. 5B illustrates a frame structure that supports the timing diagramof FIG. 5A, according to some embodiments.

FIG. 5C illustrates a flowchart for a method related to FIG. 5A and FIG.5B, according to some embodiments.

FIG. 6A illustrates a block diagram of an eUICC that stores multipleeSIMs from multiple eSIM providers, according to some embodiments.

FIG. 6B illustrates a block diagram of an eUICC that stores multipleeSIMs that are selected by a terminal using logical channels, accordingto some embodiments.

FIG. 6C illustrates a flowchart for a method related to FIG. 6A and FIG.6B, according to some embodiments.

FIG. 7 illustrates a detailed view of a computing device that can beused to implement the various components described herein, according tosome embodiments.

DETAILED DESCRIPTION

Representative applications of apparatuses and methods according to thepresently described embodiments are provided in this section. Theseexamples are being provided solely to add context and aid in theunderstanding of the described embodiments. It will thus be apparent toone skilled in the art that the presently described embodiments can bepracticed without some or all of these specific details. In otherinstances, well known process steps have not been described in detail inorder to avoid unnecessarily obscuring the presently describedembodiments. Other applications are possible, such that the followingexamples should not be taken as limiting.

A UICC is a smart card used in mobile terminals for cellular networks,including Universal Mobile Telecommunications Systems (UMTS) and LongTerm Evolution (LTE) networks. Specifically, a UICC authenticates asubscriber to a cellular network while ensuring the integrity andsecurity of the subscriber's personal data. The UICC also storesapplications for both MNO and end-user use for the correct deployment ofmobile services. The UICC is a generic multi-application platform thatis able to host several applications in parallel.

The UICC includes a SIM that is an integrated circuit that securelystores an international mobile subscriber identity (IMSI) and a relatedkey used to identify and authenticate a subscriber on a mobile telephonydevice (such as a mobile phone). In initial implementations, a SIMcircuit is embedded into a removable plastic card. This plastic card canbe called a “SIM card” and can be transferred between different mobiledevices. A SIM card contains a unique serial number, an IntegratedCircuit Card ID (ICCID), an international mobile subscriber identity(IMSI), security authentication and ciphering information, temporaryinformation related to the local network, a list of the services towhich the user has access, and authentication information (e.g.,passwords).

Over time, the role of the UICC has evolved and it has become the onlyMNO-owned part of the network residing in the hands of subscribers.Therefore, the UICC can be a useful tool for an MNO to securely provideservices to subscribers. And, due to its portability and ability to workin many mobile handsets, the UICC enables the MNO to offer networkspecific services and customization irrespective of the mobile phonebeing used. This uniqueness of the UICC allows a variety of new enhancedfeatures, all to the benefit of the MNO and the subscriber.

As previously noted, UICCs are being embedded directly into systemboards (i.e. eUICCs) of mobile devices and can be configured to managemultiple electronic SIMs (eSIMs), e.g., one eSIM for a local MNO andanother eSIM for an international MNO. These eUICCs can provide severaladvantages over traditional, removable UICCs. For example, some eUICCsinclude a rewritable memory that can facilitate eSIM updates foraccessing extended features provided by MNOs. Notably, each eSIM canhave its own file structure and applications. The problem to solve,therefore, is how to identify and access content of multiple eSIMs onthe same eUICC. For example, if the mobile device uses an existinginterface to send a read command for a file identified by a FID, therecan be a conflict since the same FID could exist within and be relevantto another eSIM. Consequently, the eUICC may not know how to access theparticular file identified by the FID.

Some other considerations include the following: standards for UICCimplementation specify that AIDs are used to identify applicationsinstalled on SIMs. An AID includes a 5-byte application provider ID andan 11-byte (or fewer) proprietary AID. The AID is determined during cardprovisioning, e.g., during a manufacturing process by a vendor. An issuewith eUICC implementation concerns the ambiguity of AIDs in a multipleeSIM environment. As previously set forth herein, an eUICC can includemultiple eSIMs. Notably, these eSIMs can come from differentun-coordinated sources, e.g., AT&T and T-Mobile. In some cases, thedifferent sources can use the same AID such that the uniqueness of theAID is not preserved across the different eSIMs. Hence, a conflict canoccur if the eUICC includes multiple eSIMs whose applications share asame AID.

To address the aforementioned issues, the embodiments described hereinset forth a technique whereby the mobile device can send to the eUICC aspecial command that includes an identifier that uniquely identifies aneSIM managed by the eUICC. Specifically, the special command can directthe eUICC to activate or deactivate the content included in the eSIM.After the eSIM is selected, the file structures and applications of theeSIM can be accessed by the mobile device using existing commands (e.g.,READ). The mobile device can select a different eSIM by firstdeactivating the active eSIM and then activating the different eSIM. Theforegoing technique can also provide compatibility benefits such that aneUICC with an active eSIM can be installed in a legacy device andsuccessfully operate in the legacy device. For this functionality, theeUICC needs to store the last-selected eSIM, and, when a boot-up of thelegacy device is carried out, the eUICC can automatically select thepreviously-selected eSIM.

As previously set forth herein, logical channels are defined in existingstandards such that the mobile device can open different logicalchannels to access different applications in an eSIM. The embodimentsset forth herein expand the functionality to allow selection ofdifferent eSIMs (as opposed to their applications) on different logicalchannels. This feature can allow the mobile device to simultaneouslyaccess multiple eSIMs and their associated content. Relative toaccessing the same application in a multiple eSIM environment, asolution can be defined utilizing the external entity coordinationprinciples of the standards. The principles include: 1) AIDs within thesame eSIM are unique, i.e., guaranteed by the eSIM vendor (similar toexisting UICC standards), and 2) AIDs from different eSIM vendors can beduplicated on the eUICC.

With eUICC OS handling, a mobile device can open multiple logicalchannels to an eUICC and avoid AID conflicts. Specifically, theapplication's associated eSIM is first associated to a given logicalchannel before the application can be selected. Thus, the eUICC OS canhave the knowledge of which eSIM is associated with an AID on a givenlogical channel. Each application can be uniquely identified by thecommand SELECT (eSIM ID, AID). Terminals (i.e., baseband processors) canbe aware of the different eSIMs managed by the eUICC, e.g., by managingthe various eSIM IDs. This solution can be implemented without majorchanges to the interface.

Accordingly, the foregoing approaches provide techniques systems toidentify and access content of different eSIMs in an eUICC. A moredetailed discussion is set forth below and described in conjunction withFIGS. 1-2, 3A, 3B, 3C, 4, 5A, 5B, 5C, 6A, 6B, 6C, and 7, whichillustrate detailed diagrams of systems and methods that can be used toimplement these techniques.

Terms relevant to embodiments set forth herein are described as follows.

-   -   AID—Application Identifier that identifies an application within        a UICC. The AID can include a registered application provider        Identifier (RID) of 5 bytes and a proprietary application        identifier extension (PIX) of up to 11 bytes. The AID of an        application can be unique on a given UICC. The AID is determined        during card provisioning, e.g., during a manufacture process by        a vendor.    -   APDU—Application Protocol Data Unit.    -   EUM—An eUICC Manufacturer.    -   ICCID—Integrated Circuit Card ID—A unique number to identify an        eSIM within an eUICC.    -   IMSI—International Mobile Subscriber Identity. The IMSI is a        unique identifier owned and issued by MNOs that identify a user        and enable mobile devices to attach to a network and use        services.    -   MCC—Mobile Country Code.    -   MNO—Mobile Network Operator. An MNO is an entity that provides        access capability and communication services to its customers        through a mobile network infrastructure.    -   OTA Platform—Over the Air Platform. An MNO-based platform used        for remote management of UICCs and enabled eSIMs on eUICCs.    -   SIM—Subscriber Identity Module.    -   eSIM—Electronic SIM. An eSIM is a software-based SIM, or “soft        SIM”. The eSIM can be a combination of a file structure, data        and applications to be provisioned onto, or present on, an        eUICC. Specifically, an eSIM, when enabled, allows access to a        specific mobile network infrastructure.    -   SM-SR—Subscription Manager Secure Routing.    -   UICC—Universal Integrated Circuit Card.    -   eUICC—an Embedded UICC.    -   USIM—Universal Subscriber Identity Module. A USIM is a network        access application (NAA) for a UMTS. The USIM on a UICC can        contain information that identifies a subscriber.

In accordance with various embodiments described herein, the terms“wireless communication device,” “wireless device,” “mobile device,”“mobile station,” and “user equipment” (UE) may be used interchangeablyherein to describe one or more common consumer electronic devices thatmay be capable of performing procedures associated with variousembodiments of the disclosure. In accordance with variousimplementations, any one of these consumer electronic devices may relateto: a cellular phone or a smart phone, a tablet computer, a laptopcomputer, a notebook computer, a personal computer, a netbook computer,a media player device, an electronic book device, a MiFi® device, awearable computing device, as well as any other type of electroniccomputing device having wireless communication capability that caninclude communication via one or more wireless communication protocolssuch as used for communication on: a wireless wide area network (WWAN),a wireless metro area network (WMAN) a wireless local area network(WLAN), a wireless personal area network (WPAN), a near fieldcommunication (NFC), a cellular wireless network, a fourth generation(4G) LTE, LTE Advanced (LTE-A), and/or 5G or other present or futuredeveloped advanced cellular wireless networks.

The wireless communication device, in some embodiments, can also operateas part of a wireless communication system, which can include a set ofclient devices, which can also be referred to as stations, clientwireless devices, or client wireless communication devices,interconnected to an access point (AP), e.g., as part of a WLAN, and/orto each other, e.g., as part of a WPAN and/or an “ad hoc” wirelessnetwork. In some embodiments, the client device can be any wirelesscommunication device that is capable of communicating via a WLANtechnology, e.g., in accordance with a wireless local area networkcommunication protocol. In some embodiments, the WLAN technology caninclude a Wi-Fi (or more generically a WLAN) wireless communicationsubsystem or radio, the Wi-Fi radio can implement an Institute ofElectrical and Electronics Engineers (IEEE) 802.11 technology, such asone or more of: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11 ac; or otherpresent or future developed IEEE 802.11 technologies.

Additionally, it should be understood that the UEs described herein maybe configured as multi-mode wireless communication devices that are alsocapable of communicating via different third generation (3G) and/orsecond generation (2G) RATs. In these scenarios, a multi-mode UE can beconfigured to prefer attachment to LTE networks offering faster datarate throughput, as compared to other 3G legacy networks offering lowerdata rate throughputs. For instance, in some implementations, amulti-mode UE may be configured to fall back to a 3G legacy network,e.g., an Evolved High Speed Packet Access (HSPA+) network or a CodeDivision Multiple Access (CDMA) 2000 Evolution-Data Only (EV-DO)network, when LTE and LTE-A networks are otherwise unavailable.

FIG. 1 illustrates a block diagram of different components of a system100 that is configured to implement the various techniques describedherein, according to some embodiments. More specifically, FIG. 1illustrates a high-level overview of the system 100, which, as shown,includes a mobile device 102, one or more base stations 112, and one ormore MNOs 114. According to one embodiment, the mobile device 102represents a wireless communication device (e.g., a smart phone, atablet, a laptop, etc.) that is capable of communicating with at leastone of the MNOs 114 via at least one of the base stations 112. As shownin FIG. 1, the mobile device 102 can include a processor 104, a memory106, an eUICC 108, and a baseband processor 110. The eUICC 108 canrepresent, for example, a hardware component that is embedded within asystem board of the mobile device 102 and is configured to provide amore flexible environment than traditional, removable UICCs. Asdescribed in greater detail below, the eUICC 108 can include a varietyof hardware/software components that enable the eUICC 108 to manageeSIMs according to the techniques described herein.

FIG. 2 illustrates a more detailed view 200 of the mobile device 102 ofFIG. 1, according to one embodiment. As shown in FIG. 2, a mobile deviceOS 202 and one or more applications 204 can execute on the mobile device102 by way of the processor 104 and the memory 106. FIG. 2 alsoillustrates the various hardware/software components described abovethat are included in the eUICC 108. More specifically, the eUICC 108 caninclude a processor 210 and a memory 212 that enable an eUICC OS 214 toexecute within the eUICC 108 and manage one or more eSIMs 216. Accordingto this configuration, the processor 104, the processor 210, and thebaseband processor 110 can work in conjunction to enable the mobiledevice 102 to access services provided by at least one of the MNOs 114.

FIG. 3A illustrates a block diagram 300 of an eSIM 302 that includes anapplication file structure 304, as well as an application_1 306 and anapplication_2 308. As illustrated in FIG. 3A, the application_1 306 andthe application_2 308 are identified by application identifiers AID_1307 and AID_2 309, respectively. The application_1 306 and theapplication_2 308 can represent different applications provided by theMNO associated with the eSIM 302. Via the application identifiers, AID_1307 and AID_2 309, the mobile device 102 can uniquely access either ofthe application_1 306 and the application_2 308. As described in greaterdetail below in conjunction with FIG. 3C, this access capability enablesthe mobile device 102 to appropriately access the application filestructure 304.

FIG. 3B illustrates a block diagram 350 of an eUICC 352 that storesmultiple eSIMs 216, which are represented in FIG. 3B as eSIM_1 354 andeSIM_2 356. In this embodiment, the applications (not illustrated inFIG. 2B) associated with the eSIM_1 354 and the eSIM_2 356 areidentified by the same application identifier, AID_1 307. Hence, anapplication in eSIM_1 354 and eSIM_2 356 can be the same application,and the application can be provided by a different MNOs. Referring toFIG. 3B, the ICCID is the same for eSIM_1 354 and eSIM_2 356. There canbe a conflict if the baseband processor 110 reads the ICCID, since aunique application identifier (hence, application) cannot be identified.Accordingly, the application file structure 304 may not be properlyidentified.

FIG. 3C illustrates a more detailed view 370 of the application filestructure 304 for eSIM 302 of FIG. 3A. The file identifier (FID) is usedto address or identify a specific file. The file types included in FIG.3C includes:

-   -   Dedicated File (DF): file containing access conditions, and,        optionally, Elementary Files (EFs) or other Dedicated Files        (DFs). DFs are referenced by FIDs.    -   Application Dedicated File (ADF): entry point to an application.        Specifically, an Application DF (ADF) is a particular DF that        contains all the DFs and EFs of an application.    -   Elementary files (EF): The valid IMSI value must be present by        default in the elementary file of the IMSI (EF IMSI) in the SIM        at production of the SIM card.    -   Master File (MF).

Applications are uniquely identified by AIDs and are obtained fromEF_(DIR). The AIDs are used to select the application. EF_(DIR), EF_(PL)and EF_(ICCID) can be mandatory and reside directly under the MF.DF_(TELECOM) can be optional, and, if present, it resides under the MF.DF_(TELECOM) can contain application-independent information.

FIG. 4 illustrates a timing diagram 400 for selecting an application ofa specific eSIM included in an eUICC. The process begins with thebaseband processor 110 of the mobile device 102 requesting a channel forcommunication. The eUICC responds with a channel selection, e.g.,channel 1. The baseband processor 110 then sends a SELECT (AID) command,requesting access to the application associated with the specified AID.The baseband processor 110 can then repeat the process to access anotherapplication; hence two parallel sessions can be active. The method canbe successful to select the proper application in an eSIM with thestructure described in FIG. 3A. However, in the case where there aremultiple eSIMs in an eUICC (e.g., FIG. 3B), a conflict can occur sincethe applications can be the same. The application may have been issuedby different MNOs and the eSIMs can have the same ICCID. Consequently,the method of FIG. 4 may not identify the proper application filestructure since the application identifiers can be the same, e.g., AID_1307.

FIG. 5A illustrates timing diagram 500 for selecting and accessing anapplication of an eSIM among multiple eSIMs that include theapplication. To begin, the baseband 110 transmits a SELECT (eSIM ID)command to the eUICC that identifies an eSIM and requests access to theeSIM. In response, the eUICC can transmit an acknowledgement message(e.g. OK) indicating an active status. If the mobile device 102 isinactive, the baseband processor 110 cannot access the eSIM. Based onMNO constraints, there may be only one eSIM active at a time. The SELECT(eSIM ID) can select the particular eSIM, e.g., eSIM1_354 or eSIM_2 356.The P1/P2 illustrated in FIG. 5B, and described below in greater detail,can include values that specify the type of SELECT command, e.g. eSIMselection. To switch between eSIM1_354 and eSIM_2 356, the basebandprocessor 110 can issue a “deselect” command, then make a new selection.For example, SELECT (P1, P2) can indicate to deselect a first eSIM, andSELECT (P3, P4) can indicate to select a second eSIM.

When the eSIM is active, the baseband processor 110 can respond with aSELECT (AID_1 307) command, which represents a request for a specificapplication (and application file structure 304). After a positiveresponse from the eUICC, the baseband processor 110 can send a SELECT(ICCID) to select the specific application. After a positive responsefrom the eUICC, the baseband processor 110 can send a READ BINARYcommand to the eUICC. The Read Binary response message can include (partof) the content of an EF with transparent structure. Additionally, theeSIM can include a subsidy lock that prevents an eUICC from beingprogrammed to select a particular MNO. The subsidy lock can restrict theMCC/MNC selection.

FIG. 5B illustrates the frame structure 550 that supports the timingdiagram 500. As shown in FIG. 5B, the frame structure 550 includes anAPDU header and eSIM ID. The APDU header includes the following frames:SELECT CLASS, INS (instruction code), P2/P2 and LEN (length). The APDUheader is included in the standards for eUICC operation. The same INScodes as included in the standards are utilized in the timing diagram500. For embodiments set forth herein, in order to provide uniqueidentification of the applications, P1/P2 frames are assigned particularvalues that are not included in the standards. Via this P1/P2programming, the baseband processor 110 is able to implement thecommunication method described in timing diagram 500. Thus, basebandprocessor 110 can select and access the file related to the applicationof interest. As previously noted, the eSIM ID is a combination of a filestructure, data and applications to be provisioned onto, or present on,an eUICC, and which allows, when enabled, the access to a specificmobile network infrastructure.

FIG. 5C illustrates a flowchart 570 for a method related to FIG. 5A andFIG. 5B. Specifically, the steps in the flowchart are implemented by thebaseband processor 110, and are carried out as follows:

1. Transmitting a SELECT (eSIM ID) command to an eUICC to an identifyeSIM—5722. After receiving an acknowledgement, transmitting a SELECT (AID1)command to the eUICC to select an application associated with theidentifier “AID1”. —5743. After receiving an acknowledgement, transmitting a SELECT (ICCID)command to confirm the ICCID and select an eSIM, including its filestructure (e.g., the application file structure 304). —5764. After receiving an acknowledgement, transmit a READ BINARY commanddirected to a specific file. —5785. Receiving the specific file.—580

Notably, this method is backward compatible (transparent) with eUICCsdesigned to standards. Specifically, the eUICC OS can remember thelast-selected eSIM, where the eSIM ID selects the eSIM, and the P1/P2coding determines the particular type of SELECT command, e.g. a selectcommand to select an eSIM.

FIG. 6A illustrates block diagram 600 of an eUICC 602 that includes aneSIM_1 604 and an eSIM_2 606. As shown in FIG. 6A, each of the eSIM_1604 and the eSIM_2 606 includes an application whose AID is “n”, whichillustrates issues that can occur when eUICCs are implemented.Specifically, the different eSIMs may come from different un-coordinatedsources, which is illustrated by eSIM Provider #1 (e.g., AT&T) and eSIMProvider #2 (e.g., T-Mobile). The different sources can use the sameAIDs for applications included in eSIMs, which, as described herein, cancause conflicts when accessing a particular application via its AID.Hence, a conflict can occur if the eUICC has multiple eSIMs with thesame applications that were provided by different sources.

A solution to the aforementioned problem is illustrated as block diagram650 in FIG. 6B. As shown in FIG. 6B, the block diagram 650 includes aneUICC 672 that includes an eSIM_1 674 and an eSIM_2 676. Each of theseeSIMs supports the same application and AID, i.e., per FIG. 6B: APP,AID=n. Here, the eUICC OS 678 is configured to coordinate thetransmission of application information to a terminal 680 (e.g., thebaseband processor 110 of FIG. 1) by the eSIM's identifier (e.g., eSIMID) and the application's identifier (AID). More specifically, the eUICCOC 678 is configured to establish a logical channel using (eSIM ID,AID). These logical channels eliminate the potential conflicts set forthherein that would otherwise occur.

The embodiment of block diagram 650 can support a number of features.AIDs within the same eSIM are unique, i.e., guaranteed by the eSIMvendor, similar to legacy UICC. However, AIDs from different eSIMs canbe duplicated on the eUICC among different eSIMs. AID conflicts can beavoided with eUICC OS 678 handling. For an application, its associatedeSIM must be first selected on a given logical channel before theapplications can be selected. Thus, the eUICC OS 678 can have theknowledge of which eSIM is associated with this AID on a given logicalchannel. Each application is uniquely identified by the command (eSIMID, AID). Terminals are aware of different eSIMs on eUICC via an eSIMID. In another embodiment, multiple eSIMs can be activated on an eUICCusing multiple logical channels. Each logical channel can simultaneouslyselect a different MNO. Therefore, the mobile device 102 can access twoor more MNOs at the same time.

FIG. 6C illustrates a flowchart 670 for a method related to FIG. 6A andFIG. 6B. The method includes the following steps, which are carried outby the eUICC OS 678 of FIG. 6B:

1. Associate an eSIM with a specific logical channel. —6722. Associate an AID with the eSIM. —6743. Direct a mobile terminal (e.g., the mobile terminal 680 of FIG. 6B)to access the AID via the logical channel with the {eSIM ID, AID}command set forth herein. Terminal 680 can be the equivalent of thebaseband processor 110 illustrated in FIG. 1 and described above ingreater detail.—676

FIG. 7 illustrates a detailed view of a computing device 700 that can beused to implement the various components described herein, according tosome embodiments. In particular, the detailed view illustrates variouscomponents that can be included in the mobile device 102 illustrated inFIG. 1. As shown in FIG. 7, the computing device 700 can include aprocessor 702 that represents a microprocessor or controller forcontrolling the overall operation of computing device 700. The computingdevice 700 can also include a user input device 708 that allows a userof the computing device 700 to interact with the computing device 700.For example, the user input device 708 can take a variety of forms, suchas a button, keypad, dial, touch screen, audio input interface,visual/image capture input interface, input in the form of sensor data,etc. Still further, the computing device 700 can include a display 710(screen display) that can be controlled by the processor 702 to displayinformation to the user. A data bus 716 can facilitate data transferbetween at least a storage device 740, the processor 702, and acontroller 713. The controller 713 can be used to interface with andcontrol different equipment through and equipment control bus 714. Thecomputing device 700 can also include a network/bus interface 711 thatcouples to a data link 712. In the case of a wireless connection, thenetwork/bus interface 711 can include a wireless transceiver.

The computing device 700 also includes a storage device 740, which cancomprise a single storage device or a plurality of storage devices, andincludes a storage management module that manages one or more partitionswithin the storage device 740. In some embodiments, storage device 740can include flash memory, semiconductor (solid state) memory or thelike. The computing device 700 can also include a Random Access Memory(RAM) 720 and a Read-Only Memory (ROM) 722. The ROM 722 can storeprograms, utilities or processes to be executed in a non-volatilemanner. The RAM 720 can provide volatile data storage, and storesinstructions related to the operation of the different softwareprocesses described herein. The computing device 700 can further includea secure element 750 that can represent the eUICC 108 illustrated inFIGS. 1-2 and described in detail herein.

The various aspects, embodiments, implementations or features of thedescribed embodiments can be used separately or in any combination.Various aspects of the described embodiments can be implemented bysoftware, hardware or a combination of hardware and software. Thedescribed embodiments can also be embodied as computer readable code ona computer readable medium. The computer readable medium is any datastorage device that can store data which can thereafter be read by acomputer system. Examples of the computer readable medium includeread-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape,hard disk drives, solid state drives, and optical data storage devices.The computer readable medium can also be distributed overnetwork-coupled computer systems so that the computer readable code isstored and executed in a distributed fashion.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the describedembodiments. However, it will be apparent to one skilled in the art thatthe specific details are not required in order to practice the describedembodiments. Thus, the foregoing descriptions of specific embodimentsare presented for purposes of illustration and description. They are notintended to be exhaustive or to limit the described embodiments to theprecise forms disclosed. It will be apparent to one of ordinary skill inthe art that many modifications and variations are possible in view ofthe above teachings.

1. A method for accessing a file in an embedded Universal IntegratedCircuit Card (eUICC) that stores electronic Subscriber Identity Modules(eSIMs), the method comprising: at the eUICC, wherein the eUICC isincluded in a mobile device that includes a processor: in response toreceiving a first command from the processor via a logical channel:selecting a first eSIM specified by the first command, and confirming anactive status of the first eSIM; in response to receiving a secondcommand from the processor via the logical channel: selecting anapplication based on an application identifier (AID) specified by thesecond command, and confirming selection of the application; and inresponse to receiving a third command from the processor via the logicalchannel: transmitting the file to the processor, wherein the file isspecified by the third command.
 2. The method as recited in claim 1,wherein each of the first command, the second command, and the thirdcommand is a SELECT command.
 3. The method as recited in claim 2,wherein the first command is a SELECT (eSIM ID) command comprising anApplication Protocol Data Unit (APDU) header and an eSIM Identifier(ID), and the APDU header comprises P1 and P2 fields that determine anelement to be selected.
 4. The method as recited in claim 2, wherein thefirst command is a SELECT (eSIM ID) command that selects the first eSIM.5. The method as recited in claim 2, wherein the second command is aSELECT (AID) command.
 6. The method as recited in claim 2, furthercomprising receiving at the eUICC a fourth command that comprises aSELECT command for an Integrated Circuit Card ID (ICCID).
 7. The methodas recited in claim 1, wherein the third command is a READ Binarycommand.
 8. The method as recited in claim 1, wherein the first eSIM isthe only active eSIM in the eUICC.
 9. The method as recited in claim 1,wherein the first eSIM is one of two or more active eSIMs in the eUICC.10. The method as recited in claim 1, wherein the processor selects asecond eSIM by deactivating the first eSIM and subsequently activatingthe second eSIM.
 11. The method as recited in claim 1, wherein the firsteSIM comprises a subsidy lock that prevents the eUICC from beingprogrammed to select a particular Mobile Network Operator (MNO).
 12. Themethod as in claim 1, wherein the first command directs the eUICC toactivate or to deactivate content of the first eSIM.
 13. A mobiledevice, comprising: an embedded Universal Integrated Circuit Card(eUICC) that includes two or more electronic Subscriber Identity Modules(eSIMs); a baseband processor; an application processor; and at leastone memory configured to store instructions that, when executed by theapplication processor, cause the baseband processor to: transmit acommand to the eUICC, wherein the command: identifies a first eSIM ofthe two or more eSIMs, and directs the eUICC to activate or deactivatecontent of the first eSIM; and when the first eSIM is active: select thefirst eSIM, and access application file structures of the first eSIM viaa logical channel.
 14. The mobile device as recited in claim 13, whereinat least two of the two or more eSIMs are active within the eUICCsimultaneously.
 15. The mobile device as recited in claim 13, whereinthe baseband processor, using multiple logical channels, simultaneouslyaccesses at least two of the two or more eSIMs.
 16. The mobile device asrecited in claim 13, wherein the command is a SELECT (eSIM ID) commandthat comprises an Application Protocol Data Unit (APDU) header and aneSIM Identifier (ID), and the APDU header comprises P1 and P2 fieldsthat determine an element to be selected.
 17. A non-transitory computerreadable storage medium configured to store instructions that, whenexecuted by a baseband processor included in a mobile device, cause themobile device to route commands to specific electronic SubscriberIdentity Modules (eSIMs) managed by an embedded Universal IntegratedCircuit Card (eUICC) included in the mobile device, by carrying outsteps that include: transmitting a first command via a logical channelto select a first eSIM; transmitting a second command via the logicalchannel to select an application of the first eSIM based on anapplication identifier (AID); transmitting a third command via a logicalchannel to confirm an Integrated Circuit Card ID (ICCID) associated withthe first eSIM; and receiving binary data from an application dedicatedfile (ADF) of the first eSIM.
 18. The non-transitory computer readablestorage medium as recited in claim 17, wherein each of the firstcommand, the second command, and the third command is a SELECT command,and the first command is a SELECT (eSIM ID) command.
 19. Thenon-transitory computer readable storage medium as recited in claim 17,wherein at least two eSIMs are active simultaneously within the eUICC.20. The non-transitory computer readable storage medium as recited inclaim 17, wherein the mobile device selects a second eSIM bydeactivating the first eSIM and subsequently activating the second eSIM.